Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0496

reference
157-tree-1
name
0496
tree-preservation-order

undefined

157-tpo-1
uprn
address-text
point
POINT (-1.009340 50.851666)
geometry
MULTIPOLYGON (((-1.009284 50.851660,-1.009286 50.851671,-1.009294 50.851681,-1.009307 50.851689,-1.009322 50.851694,-1.009340 50.851696,-1.009357 50.851695,-1.009373 50.851690,-1.009386 50.851682,-1.009394 50.851672,-1.009397 50.851661,-1.009395 50.851650,-1.009387 50.851640,-1.009375 50.851632,-1.009359 50.851626,-1.009341 50.851624,-1.009324 50.851626,-1.009308 50.851631,-1.009295 50.851639,-1.009287 50.851649,-1.009284 50.851660)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL